Hi Sam,

I think a big clue is that Dynomotion VB.NET runs ok.

Compare project settings?

Maybe try copying/targeting your app into the KMotion/Debug Directory.

Maybe try Released Version.

Possibly an issue with the VS2012 run time distributables?

Maybe an issue with missing the USB interface FTD2XX.dll?

Regards

TK

All good items to check. I will look into each of those....although I know the project settings haven't changed between machine for my app since I tried the (already) compiled executable that I knew worked previously and still works on the old OSes.

Although I know USB is working (for other devices) on the WIndows 10 machine, what can you tell me about the FTD2xx.dll you suspect? Is that something installed with KMotion?

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

 

On 10/7/2015 4:09 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi Sam,

I think a big clue is that Dynomotion VB.NET runs ok.

Compare project settings?

Maybe try copying/targeting your app into the KMotion/Debug Directory.

Maybe try Released Version.

Possibly an issue with the VS2012 run time distributables?

Maybe an issue with missing the USB interface FTD2XX.dll?

Regards

TK

All good items to check. I will look into each of those....although I know the project settings haven't changed between machine for my app since I tried the (already) compiled executable that I knew worked previously and still works on the old OSes.

Although I know USB is working (for other devices) on the WIndows 10 machine, what can you tell me about the FTD2xx.dll you suspect? Is that something installed with KMotion?

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

>Are there any known incompatibility issues with Windows 10? I haven't
>analyzed it a lot yet, but I have noticed the following....
>
>-A Windows 7 machine upgraded to Windows 10 continues to run KFlop
>dotnet apps such as Jogger.net just fine.
>-A Windows 10 machine that was a clean install is giving "side-by-side
>configuration" errors when trying to run the same apps.

 

On Tue, 6 Oct 2015 21:10:29 -0400, you wrote:

>Are there any known incompatibility issues with Windows 10? I haven't
>analyzed it a lot yet, but I have noticed the following....
>
>-A Windows 7 machine upgraded to Windows 10 continues to run KFlop
>dotnet apps such as Jogger.net just fine.
>-A Windows 10 machine that was a clean install is giving "side-by-side
>configuration" errors when trying to run the same apps.

Have you checked on Google for side-by-side configuration errors?

Usually C++ library missing.

As a quick test, turn of UAC, and download redistributable packages and
install.

Steve Blackmore

Yes, I believe the earlier "side-by-side" issue with Jogger was because I was running the debug version of Jogger.net and Windows 10 no longer includes the debug libraries by default, nor are they installed by the C++ redistributables. That one was a bit of a red herring and I don't believe has anything to do with the missing kmotion.dll errors I am now getting.

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

 

Hi Sam,

The FTD2XX.dll is a necessary dll used to talk to the FTDi Windows Driver.  It is installed with KMotion in the Release and Debug folders.  Installing the Device driver might also put it in the windows directories.  Since it seems you are running from your own folders maybe it is somehow missing?

Good to know.
Copying the FTD2XX.dll into my app's path eliminated the

"An error occurred creating the form. See Exception.InnerException for details.  The error is: Dll Not Found Exception thrown :  Caller - [KMotion_dotNet.KM_Controller] :: Member - [KM_Controller]"

error that was occuring. Since my Windows 7 and Windows 7-upgraded to 10 machines did not have this problem AND I did NOT have the FTD2XX.dll file in my app's path on those machines, I'm wondering why this wasn't a problem before? I wouldn't have placed the FTD2XX.dll onto my machine for anything else so unless the KMOTION earlier installers placed it somewhere on the machine I don't know how it would have worked previously, but it does....?

So after copying FTD2XX.dll to my minimal app path, I added a bit of code to check for boards and other issues. While I'm not getting the previously mentioned initial errors, this code:

Dim AllBoards As Integer()
Dim NumberOfBoards As Int32
AllBoards = ThisController.GetBoards(NumberOfBoards)
Console.WriteLine(AllBoards.Length)   
Console.WriteLine(NumberOfBoards)  

displays:
256
0

It seems that the board is not connecting. I then ran KMotion which displays "Disconnected" in it's title bar. When plugged in, the board does it's blinking/tests and appears fine and Windows 10 plays a little sound to show it has connected, but none of the KMotion apps can actually connect...?

Regards

On 10/7/2015 2:50 PM, 'Marrocco, Sam' SMarrocco@... [DynoMotion] wrote:

 

On 10/7/2015 4:09 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi Sam,

I think a big clue is that Dynomotion VB.NET runs ok.

Compare project settings?

Maybe try copying/targeting your app into the KMotion/Debug Directory.

Maybe try Released Version.

Possibly an issue with the VS2012 run time distributables?

Maybe an issue with missing the USB interface FTD2XX.dll?

Regards

TK

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

 

On 10/7/2015 6:56 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi Sam,

The FTD2XX.dll is a necessary dll used to talk to the FTDi Windows Driver.  It is installed with KMotion in the Release and Debug folders.  Installing the Device driver might also put it in the windows directories.  Since it seems you are running from your own folders maybe it is somehow missing?

Good to know.
Copying the FTD2XX.dll into my app's path eliminated the

"An error occurred creating the form. See Exception.InnerException for details.  The error is: Dll Not Found Exception thrown :  Caller - [KMotion_dotNet.KM_Controller] :: Member - [KM_Controller]"

error that was occuring. Since my Windows 7 and Windows 7-upgraded to 10 machines did not have this problem AND I did NOT have the FTD2XX.dll file in my app's path on those machines, I'm wondering why this wasn't a problem before? I wouldn't have placed the FTD2XX.dll onto my machine for anything else so unless the KMOTION earlier installers placed it somewhere on the machine I don't know how it would have worked previously, but it does....?

So after copying FTD2XX.dll to my minimal app path, I added a bit of code to check for boards and other issues. While I'm not getting the previously mentioned initial errors, this code:

Dim AllBoards As Integer()
Dim NumberOfBoards As Int32
AllBoards = ThisController.GetBoards(NumberOfBoards)
Console.WriteLine(AllBoards.Length)   
Console.WriteLine(NumberOfBoards)  

displays:
256
0

It seems that the board is not connecting. I then ran KMotion which displays "Disconnected" in it's title bar. When plugged in, the board does it's blinking/tests and appears fine and Windows 10 plays a little sound to show it has connected, but none of the KMotion apps can actually connect...?

Regards

On 10/7/2015 2:50 PM, 'Marrocco, Sam' SMarrocco@... [DynoMotion] wrote:

 

On 10/7/2015 4:09 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi Sam,

I think a big clue is that Dynomotion VB.NET runs ok.

Compare project settings?

Maybe try copying/targeting your app into the KMotion/Debug Directory.

Maybe try Released Version.

Possibly an issue with the VS2012 run time distributables?

Maybe an issue with missing the USB interface FTD2XX.dll?

Regards

TK

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com

 

Hi Sam,

Have you loaded the USB Driver?  You must temporarily disable Windows Driver Signing Enforcement to do this.

What does Device Manager indicate?  That may be the reason FTD2XX.dll wasn't on your system as well.

Regards
TK

On 10/8/2015 9:06 AM, 'Marrocco, Sam' SMarrocco@... [DynoMotion] wrote:

 

On 10/7/2015 6:56 PM, Tom Kerekes tk@... [DynoMotion] wrote:

 

Hi Sam,

The FTD2XX.dll is a necessary dll used to talk to the FTDi Windows Driver.  It is installed with KMotion in the Release and Debug folders.  Installing the Device driver might also put it in the windows directories.  Since it seems you are running from your own folders maybe it is somehow missing?

While it appeared that copying the FTD2XX.dll file into my app's folder was making things better, I think it was only distracting from the main problem, which appears to be that the KFlop driver was not being installed properly.

I booted the machine into the new double-secret mode that allows you to successfully install drivers. I then did a (successful) install of the KFLOP driver by right-clicking on C:\KMotion433q\USB Driver\KFLOP.inf and selecting "Install". Although it did say "successfully installed", a few moments later windows informed me that it could not install unsigned drivers with another dialog box. However, checking the Device Manager showed that the KFlop was now detected and the driver installed.

I then removed the (previously) copied FTD2XX.dll file from my app's path. The app now runs successfully. I would suspect that your were correct, Tom, that the FTD2xx.DLL *is* being installed to the windows/system folders for use when the KFLOP driver is successfully installed, which it was not, and is why moving the FTD2xx.DLL seemed to help.

This Windows 10 driver "filtering" is definitely something to look out for in the future. Thanks for all the help!

--

sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink

248 548 2500 w
248 910 3344 c

ringsidecreative.com